MFENCE and LFENCE micro-architectural implementation method and system

ABSTRACT

A system and method for fencing memory accesses. Memory loads can be fenced, or all memory access can be fenced. The system receives a fencing instruction that separates memory access instructions into older accesses and newer accesses. A buffer within the memory ordering unit is allocated to the instruction. The access instructions newer than the fencing instruction are stalled. The older access instructions are gradually retired. When all older memory accesses are retired, the fencing instruction is dispatched from the buffer.

BACKGROUND

[0001] 1. Field of the Invention

[0002] The present invention relates in general to computer architecture and in particular to a method and system of organizing memory access.

[0003] 2. Description of the Related Art

[0004] Video, graphics, communications and multimedia applications require high throughput processing power. As consumers increasingly demand these applications, microprocessors have been tailored to accelerate multimedia and communications applications.

[0005] Media extensions, such as the Intel MMX™ technology, introduced an architecture and instructions to enhance the performance of advanced media and communications applications, while preserving compatibility with existing software and operating systems. The new instructions operated in parallel on multiple data elements packed into 64-bit quantities. The instructions accelerated the performance of applications with computationally intensive algorithms that performed localized, reoccurring operations on small native data. These multimedia applications included: motion video, combined graphics with video, image processing, audio synthesis, speech synthesis and compression, telephony, video conferencing, and two and three-dimensional graphics applications.

[0006] Although parallel operations on data can accelerate overall system throughput, a problem occurs when memory is shared and communicated among processors. For example, suppose a processor performs data decompression of a video image. If a memory load or store occurs from an external agent or another processor while the data image is not complete, the external agent would receive incomplete or corrupt image data. Moreover, the situation becomes particularly acute, as many multimedia applications now require communications and data exchange between many external agents, such as external graphics processors.

[0007] Thus, what is needed is a method and system that allow computer architecture to perform computations in parallel, yet guarantee the integrity of a memory access or store.

SUMMARY

[0008] The load fencing process and system receives a load fencing instruction that separates memory load instructions into older loads and newer loads. A load buffer within the memory ordering unit is allocated to the instruction. The load instructions newer than the load fencing instruction are stalled. The older load instructions are gradually retired. When all older loads from the memory subsystem are retired, the load fencing instruction is dispatched.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The inventions claimed herein will be described in detail with reference to the drawings in which reference characters identify correspondingly throughout and wherein:

[0010]FIG. 1 illustrates instruction flow through microprocessor architecture;

[0011]FIG. 2 flowcharts an embodiment of the load fencing (LFENCE) process with senior loads retiring from the L1 cache controller;

[0012]FIG. 3 flowcharts an embodiment of the memory fencing (MFENCE) process with senior loads retiring from the L1 cache controller;

[0013]FIG. 4 flowcharts an embodiment of the load fencing (LFENCE) process with senior loads retiring from the memory ordering unit; and

[0014]FIG. 5 flowcharts an embodiment of the memory fencing (MFENCE) process with senior loads retiring from the memory-ordering unit.

DETAILED DESCRIPTION

[0015] It is possible to order the execution of memory access in computer architecture. The method and system of implementing this memory “fencing” will be discussed in the terms of two memory fence instructions—a memory fence (“MFENCE”) and a memory load fence (“LFENCE”). These instructions complement the use of SFENCE, an existing Intel MMX2™ instruction. Neither instruction has an associated address or data operand.

[0016] MFENCE guarantees that every memory access that precedes it, in program order, is globally visible prior to any memory instruction that follows it, in program order. Memory accesses include loads, stores, and other fence and serializing instructions. MFENCE is therefore strongly ordered with respect to other memory instructions, regardless of their memory type.

[0017] In the Intel family of P6 microprocessors (for example, Pentium II™, and Celeron™ processors), a micro-operation, “store_address_fence,” serializes prior and subsequent micro-operations. The micro-operation dispatches “at-retirement,” and it executes only once all older operations have fully completed; i.e., all L1 cache controller buffers are empty. Similarly, MFENCE is also dispatched “at-retirement”; however, MFENCE provides slightly better performance than the existing “store_address_fence,” since it is allowed to execute once all prior instructions have been globally observed, not necessarily completed.

[0018] The LFENCE instruction can be contrasted to SFENCE. SFENCE also dispatches “at-retirement,” and it executes once all older stores, in program order, have been globally is observed; however, it does not fence loads. LFENCE guarantees that every load that precedes it, in program order, is globally visible prior to any load that follows it, in program order. It prevents speculative loads from passing the LFENCE instruction. LFENCE is also ordered with respect to other LFENCE instructions, MFENCE instructions, and serializing instructions, such as CPUID. It is not ordered with respect to stores or the SFENCE instruction. Like with MFENCE, the behavior of LFENCE is independent of its memory type.

[0019] In FIG. 1, an example microprocessor memory and bus subsystem is depicted with the flow of memory loads and stores. FIG. 1 shows two cache levels in the microprocessor:

[0020] an on-chip (“L1”) cache being the cache level closest to the processor, and second level (“L2”) cache being the cache level farthest from the processor. An instruction fetch unit 102 fetches macroinstructions for an instructions decoder unit 104. The decoder unit 104 decodes the macroinstructions into a stream of microinstructions, which are forwarded to a reservation station 106, and a reorder buffer and register file 108. As an instruction enters the memory subsystem, it is allocated in the load 112 or store buffer 114, depending on whether it is a read or a write memory macroinstruction, respectively. In the unit of the memory subsystem where such buffers reside, the instruction goes through memory ordering checks by the memory ordering unit 110. If no memory dependencies exist, the instruction is dispatched to the next unit in the memory subsystem after undergoing the physical address translation. At the L1 cache controller 120, it is determined whether there is an L1 cache hit or miss. In the case of a miss, the instruction is allocated into a set of buffers, from where it is dispatched to the bus sub-system 140 of the microprocessor. In case of a cacheable load miss, the instruction is sent to read buffers, 122, or in the case of a cacheable store miss, the instruction is sent to write buffers 130. The write buffers may be either weakly ordered write combining buffers 132 or non-write combining buffers 134. In the bus controller unit 140, the read or write micro-operation is allocated into an out-of-order queue 144. If the micro-operation is cacheable, the L2 cache 146 is checked for a hit/miss. If a miss, the instruction is sent through an in-order queue 142 to the frontside bus 150 to retrieve or update the desired data from main memory.

[0021] As it can be seen in FIG. 1, the MFENCE and LFENCE flow through the microprocessor is slightly different to that of a memory load or store. MFENCE and LFENCE never check the L1 cache 124, 126 or the L2 cache 146 and never allocate a buffer in the L1 cache controller 120. Consequently, neither instruction ever reaches the bus controller 140. They are last allocated in a hardware structure in the memory-ordering unit 110; i.e., store and load buffers 114, 112 for MFENCE and LFENCE, respectively. LFENCE is dispatched on the memory ordering unit 110 load port, and MFENCE is dispatched on the memory ordering unit 110 store port. Their data fields are always ignored by the memory subsystem.

[0022] The memory ordering constraints of the MFENCE and LFENCE macro-instructions are seen below in Tables 1 and 2 and are compared with SFENCE. TABLE 1 Memory ordering of instructions with respect to later MFENCE and LFENCE macroinstructions Later access Earlier access MFENCE LFENCE SFENCE Non-senior load N N  Y* Senior load N N  Y* Store N Y N CLFLUSH N  Y*  Y* MFENCE N N N LFENCE N N  Y* SFENCE N  Y* N

[0023] TABLE 2 Memory ordering of instructions with respect to earlier MFENCE and LFENCE macroinstructions Earlier Later access access Non-senior Load Senior load Store CLFLUSH MFENCE LFENCE SFENCE MFENCE N N N N N N N LFENCE N N  Y*  Y* N N  Y* SFENCE  Y*  Y* N  Y* N  Y* N

[0024] When using fencing instructions other than MFENCE, such as LFENCE or SFENCE, strong ordering with respect to a cache line flush (“CLFLUSH”) macroinstruction cannot be guaranteed. The former two instructions only serialize loads (LFENCE) or stores (SFENCE), respectively, but not both.

[0025] Take for example the code below. Masked stores write to address [x]. All instructions except MFENCE target cache line at address [x]:

[0026] PREFETCH [x]

[0027] MASKMOVQ data 1, mask 1

[0028] MFENCE

[0029] CLFLUSH [x]

[0030] MFENCE

[0031] MASQMOVQ data 2, mask 2

[0032] In the example code above, the intent of the programmer is to prefetch line [x] into the L1 cache. Then, write data1 (assuming mask1=all 1's) to line [x], flush the line out to main memory, and write data2 (assuming mask2=all 1's) to line [x] in main memory (line [x] no longer is in the cache hierarchy).

[0033] However, if the SFENCE macroinstruction were used in place of MFENCE, the PREFETCH macroinstruction could potentially execute after the cache line flush macroinstruction. In this case, the final location of the data would be in the cache hierarchy, with the intent of the cache line flush having been nullified. The SFENCE macroinstruction serializes stores with respect to itself; but it allows senior loads, such as the PREFETCH macroinstruction, to be executed out-of-order.

[0034] Alternatively, if the LFENCE macroinstruction were used in place of MFENCE, the cache line flush macroinstruction could potentially execute out of order with respect to the older MASKMOVQ. This behavior would nullify the effect of the PREFETCH macroinstruction. Both MASKMOVQ instructions would update main memory. Dependent on the hardware implementation chosen for LFENCE, a cache line flush could also potentially execute out of order with respect to the PREFETCH macroinstruction. In this case, the original intent of the cache line flush macroinstruction is never achieved, and the final location of the line is the local cache.

[0035] MFENCE is the only of three fencing macroinstructions (i.e., MFENCE, LFENCE and SFENCE) that will serialize all memory instructions, including a cache line flush. Using MFENCE, strong ordering is achieved, as shown in the above example code.

[0036] There are two alternative hardware embodiments for the MFENCE and LFENCE macroinstructions based on the behavior of senior loads. The latter can either retire from the L1 cache controller unit 120 or from the memory-ordering unit 110, depending on the hardware implementation chosen. In either case, “senior loads” are retired from the memory subsystem of the microprocessor prior to execution.

[0037] Turning to FIG. 2, a flowchart depicts a load fence (LFENCE) embodiment where senior loads retire from the L1 cache controller unit 120. In such an embodiment, senior loads cannot be retired unless they are dispatched from the memory ordering unit 110, and accepted by the L1 cache controller 120. This is the case where there is no L1 cache controller 120 blocking condition. The senior load is retired from the memory subsystem upon a L1 cache hit; alternatively in the case of a L1 cache miss, the senior load is retired upon allocation of the incoming senior load in a read buffer 122 in the L1 cache controller 120.

[0038] Initially, the instruction fetch unit 102 fetches an LFENCE macroinstruction, block 202. The instruction is decoded by the instruction decoder unit 104 into its constituent microinstruction operation, block 204. In block 206, an entry is allocated into the reservation station 106. A load buffer 112 is allocated in the memory ordering unit 110, block 208. The load dispatches that follow (in program order) the LFENCE instruction are stalled, block 210. The process moves to block 212, when the LFENCE is ready to dispatch.

[0039] If not all older loads in program order are retired from the memory subsystem, as determined by decision block 214, the LFENCE is dispatched and older loads are retired in block 216, then the flow returns to block 210.

[0040] “At-retirement” loads are not dispatched from the memory ordering unit 110 until all older loads have been retired from the memory subsystem, as determined by decision block 214. Therefore, with this hardware embodiment for senior loads, “at-retirement” loads dispatch from the memory-ordering unit 110 in program order with respect to other loads, block 218. Flow continues to decision block 220.

[0041] In decision block 220, it is determined whether all read buffers 122, in the L1 cache controller 120, are globally observed. If not all read buffers 122 are globally observed, the L1 cache controller 120 blocks or aborts the LFENCE instruction in block 222, and then flow returns to block 210.

[0042] If all read buffers 122 are globally observed, as determined by block 220, flow ends in block 224, when the LFENCE is deallocated from the load buffer 112 in the memory ordering unit 110. The L1 cache controller 120 treats the LFENCE instruction as a non-operation (NOP), and the LFENCE is retired from the L1 cache controller 120.

[0043] It is worth noting that the LFENCE does not execute out of order with respect to older loads, because the LFENCE instruction is dispatched “at-retirement” from the memory-ordering unit 110 on the load port. Thus, all older loads in program order have been retired from the memory subsystem of the microprocessor.

[0044] Similarly, newer loads do not execute out of order with respect to a LFENCE. A new control bit is added to each entry in the load buffers 112 in the memory-ordering unit 110. It is set when a given entry is allocated to service a LFENCE operation; otherwise, it is cleared. The tail pointer points to the next entry to be deallocated form the load buffer 112, which is the oldest load in the machine. This implies that all older loads have been completed and deallocated. The corresponding dispatch is stalled if any load buffer 112 entry between the tail pointer and the L1 cache controller 120 dispatch entry has the control bit set. The control bit being set indicates that there is an LFENCE operation between the oldest load in the machine and the load for which a dispatch was attempted. The latter load cannot be dispatched out of order with respect to the LFENCE, and it is consequently stalled until retirement of the LFENCE. The retirement of the LFENCE occurs the tail pointer passes LFENCE instruction.

[0045] A memory fence (MFENCE) can be thought of as a more restrictive embodiment of the load fence in which an LFENCE dispatches an “all blocking” micro-operation from the store port. In such an embodiment, shown in FIG. 3, the MFENCE instruction is allocated in the store buffers 114, instead of load buffers 112. It has the disadvantage of serializing both loads and stores. This can be thought of as mapping the LFENCE micro-operation to the MFENCE micro-operation.

[0046] In FIG. 3, a flowchart depicts a memory fence (MFENCE) embodiment where senior loads and stores retire from the L1 cache controller unit 120. In such an embodiment, senior instructions cannot be deallocated from the store buffer in the memory unit unless they are dispatched from the memory-ordering unit 110, and accepted by the L1 cache controller 120. This is the case where there is no L1 cache controller 120 blocking condition. The senior instructions are retired from the memory subsystem upon a L1 cache hit; alternatively in the case of a L1 cache miss, the senior instructions are retired upon allocation of the incoming senior instructions in a read buffer 122 in the L1 cache controller 120.

[0047] Initially, the instruction fetch unit 102 fetches an MFENCE macroinstruction, block 302. The instruction is decoded by the instruction decoder unit 104 into its constituent microinstruction operation, block 304. In block 306, an entry is allocated into the reservation station 106. A store buffer 114 is allocated in the memory ordering unit 110, block 308. The store dispatches that follow (in program order) the MFENCE instruction are stalled, block 310. The process moves to block 312, when the MFENCE is ready to dispatch.

[0048] If not all older memory access instructions in program order are retired from the memory subsystem, as determined by decision block 314, the MFENCE is dispatched and older instructions are retired in block 316, then the flow returns to block 310.

[0049] Decision block 314 determines whether all older memory access instructions have been retired from the memory subsystem before “at-retirement” instructions are dispatched from the memory ordering unit 110. Therefore, with this hardware embodiment for senior instructions, “at-retirement” instructions dispatch from the memory-ordering unit 110 in program order with respect to other instructions, block 318. Flow continues to decision block 320.

[0050] In decision block 320, it is determined whether any outstanding read buffers 122 or write buffers 130, in the L1 cache controller 120, are globally observed. If not all the buffers 122, 130 are globally observed, flow moves to block 322. In decision block 322, it is determined whether any write combining buffers 132 in the L1 cache controller 120 are not in the eviction process. If write combining buffers 132 are in the eviction process, the L1 cache controller 120 blocks or aborts the MFENCE instruction in block 326, and then flow returns to block 310. If there are no write combining buffers 132 in the eviction, process, all outstanding write combining buffers 132 are evicted, block 324, and flow moves to block 326.

[0051] Returning to decision block 320, if all outstanding read buffers 122 or write buffers 130 are already globally observed, flow ends in block 328, when the MFENCE is deallocated from the store buffer 114 in the memory ordering unit 110. The L1 cache controller 120 treats the MFENCE instruction as a non-operation (NOP), and the MFENCE is retired from the L1 cache controller 120.

[0052] To ensure the MFENCE instruction does not execute out of order with respect to earlier memory instructions, and later memory instructions do not execute out of order with respect to MFENCE, MFENCE is dispatched as an “all blocking” micro-operation from the memory ordering unit 110 on the store port.

[0053] In an alternate hardware embodiment, senior loads retire from the memory-ordering unit 110. In this embodiment, depicted in FIG. 4, senior loads can be retired upon their first dispatch from the memory-ordering unit 110, even if the L1 cache controller 120 did not accept the senior load. Such an example includes an L1 cache controller 120 blocking condition. In this implementation, it is possible for a senior load to be retired from the memory subsystem of the microprocessor, and an entry in the load buffer 112 can still remain allocated with this senior load for subsequent re-dispatch to the L1 cache controller 120. It is therefore possible for a younger “at-retirement” load (i.e., an uncachable load) to execute out of order with respect to an older senior load.

[0054] The instruction fetch unit 102 fetches an LFENCE macroinstruction, block 402. The instruction is decoded by the instruction decoder unit 104 into its constituent microinstruction operation, block 404. In block 406, an entry is allocated into the reservation station 106. A load buffer 112 is allocated in the memory ordering unit 110, block 408. The load dispatches that follow (in program order) the LFENCE instruction are stalled, block 410. The process moves to block 412, when the LFENCE is ready to dispatch.

[0055] If not all older loads in program order are retired from the memory subsystem, and the load buffer 112 tail pointer is pointing to the LFENCE instruction, as determined by decision block 414, the LFENCE is dispatched and older loads are retired in block 416, then the flow returns to block 410.

[0056] “At-retirement” loads are not dispatched from the memory ordering unit 110 until all older loads have been retired from the memory subsystem, and the load buffer tail pointer points to the LFENCE instruction, as determined by decision block 414. Therefore, with this hardware embodiment for senior loads, “at-retirement” loads dispatch from the memory-ordering unit 110 in program order with respect to other loads, block 418. Flow continues to decision block 420.

[0057] In decision block 420, it is determined whether all read buffers 122, in the L1 cache controller 120, are globally observed. If not all read buffers 422 are globally observed, the L1 cache controller 120 blocks or aborts the LFENCE instruction in block 422, and then flow returns to block 410.

[0058] If all read buffers 122 are globally observed, as determined by block 420, flow ends in block 424, when the LFENCE is deallocated from the load buffer 112 in the memory ordering unit 110. The L1 cache controller 120 treats the LFENCE instruction as a non-operation (NOP), and the LFENCE is retired from the L1 cache controller 120.

[0059] It is worth noting that the LFENCE does not execute out of order with respect to older loads, because the LFENCE instruction is not dispatched from the memory-ordering unit until two conditions are met. The first condition is that the corresponding load buffer entry is pointed to by the reorder buffer retirement pointer. The second condition is that the corresponding load buffer entry is also pointed to by the load buffer tail pointer. The retirement pointer indicates all older instructions have been retired, and the tail pointer points to the next entry to be deallocated from the load buffer. The tail pointer can also be thought of as pointing to the oldest load in the machine.

[0060] Furthermore, newer loads do not execute out of order with respect to an LFENCE instruction. This is because LFENCE uses the same implementation as for the case described earlier with senior loads retiring from the L1 cache controller. A control bit is added for each load buffer entry. Prior to a load dispatch, the value of this control bit is checked for each entry between the one pointed to by the tail pointer and the one for which a memory dispatch is being attempted.

[0061] Similarly, an MFENCE instruction can be implemented where senior loads retire from the memory-ordering unit 110. In this embodiment, an MFENCE does not execute out of order with respect to older memory instructions, nor do any younger memory instructions execute out of order with respect to the MFENCE. In such an embodiment, an additional micro-operation is required to implement the MFENCE. In an embodiment described earlier for supporting MFENCE with senior loads retiring from the L1 cache controller, the MFENCE could be implemented as a set of two micro-operations on the store port. Those two micro-operations are “store_data” (the data is ignored) and “store_address_mfence”. In the current embodiment, three micro-operations are needed to implement MFENCE and support senior loads retiring from the memory-ordering unit. These micro-operations are: an “LFENCE” micro-operation, a “Store-data” micro-operation, and a “Store address_MFENCE” micro-operation. The first micro-operation can be the same as the LFENCE embodiment described to support senior loads retiring from the memory-ordering unit 110. The last two micro-operations are the same as those used to implement MFENCE and support senior loads retiring from the L1 cache controller 110. The micro-operations are “all blocking” micro-operations dispatched from the memory ordering unit on the store port.

[0062] As shown in FIG. 5, the instruction fetch unit 102 fetches an MFENCE macroinstruction, block 502. The instruction is decoded by the instruction decoder unit 104 into its constituent microinstruction operations, block 504. In block 506, an entry is allocated into the reservation station 106. A load buffer 112 and store buffer 114 entries are allocated in the memory ordering unit 110, block 508. The load dispatches that follow (in program order) the LFENCE instruction are stalled and then the MFENCE micro-operation is performed, block 510. The process moves to block 512, when the LFENCE stalls the dispatch of the MFENCE micro-operation. In block 514, the LFENCE is ready to dispatch.

[0063] If not all older loads in program order are retired from the memory subsystem, and the load buffer 112 tail pointer points to the LFENCE instruction, as determined by decision block 516, the LFENCE is dispatched and older loads are retired in block 518, then the flow returns to block 510.

[0064] Conversely, the “at-retirement” loads are dispatched from the memory ordering unit 110 when all older loads have been retired from the memory subsystem and the load buffer 112 tail pointer points to the LFENCE instruction, as determined by decision block 516. Therefore, with this hardware embodiment for senior loads, “at-retirement” loads dispatch from the L1 cache controller on the load port, block 520. Flow continues to decision block 522.

[0065] In decision block 522, it is determined whether any outstanding read buffers 122, in the L1 cache controller 120, are globally observed. If not all the read buffers 122, are globally observed, flow moves to block 524. At block 524, the L1 cache controller the L1 cache controller 120 blocks or aborts the LFENCE instruction.

[0066] If all the read buffers 122, are globally observed, flow moves to block 526.

[0067] At block 526, the L1 cache controller 120 treats the LFENCE instruction as a non-operation (NOP), and the LFENCE is retired from the L1 cache controller 120. Flow continues at block 528.

[0068] All instruction dispatches following the MFENCE, in program order, are stalled, block 528.

[0069] The process moves to block 530, when the MFENCE is ready to dispatch.

[0070] If not all older memory access instructions in program order are retired from the memory subsystem, as determined by decision block 532, the MFENCE is dispatched and older memory access instructions are retired in block 534, then the flow returns to block 528.

[0071] Decision block 532 determines whether all older instructions have been retired from the memory subsystem before “at-retirement” instructions are dispatched from the memory ordering unit 110. Therefore, with this hardware embodiment for senior memory instructions, “at-retirement” instructions dispatch from the memory-ordering unit 110 in program order with respect to other instructions, block 536. Flow continues to decision block S38.

[0072] In decision block 538, it is determined whether any outstanding read buffers 122 or write buffers 130, in the L1 cache controller 120, are globally observed. If not all the buffers 122, 130 are globally observed, flow moves to block 540.

[0073] At decision block 540, it is determined whether any write combining buffers 132 in the L1 cache controller 120 are not in the eviction process. If write combining buffers 132 are in the eviction process, the L1 cache controller 120 blocks or aborts the MFENCE instruction in block 544, and then flow returns to block 528. If there are no write combining buffers 132 in the eviction, process, all outstanding write combining buffers 132 are evicted, block 542, and flow moves to block 544.

[0074] Returning to decision block 538, if all outstanding read buffers 122 or write buffers 130 are already globally observed, flow ends in block 546, when the MFENCE is deallocated from the store buffer 114 in the memory ordering unit 110. The L1 cache controller 120 treats the MFENCE instruction as a non-operation (NOP), and the MFENCE is retired from the L1 cache controller 120.

[0075] Regardless of the implementation, LFENCE is always dispatched from the memory-ordering unit 110 to the rest of the memory subsystem once it is guaranteed to be the oldest load in the machine.

[0076] Upon its dispatch from the memory-ordering unit 110, the LFENCE instruction is blocked by the L1 cache controller 120 if there are read buffers 122 not yet globally observed. The memory ordering unit 110 keeps redispatching the LFENCE until all read buffers 122 in the L1 cache controller 120 are globally observed. Once the L1 cache controller 120 accepts the incoming LFENCE, it is retired from the memory subsystem, and it is treated as a non-operation. Consequently, the instruction is never allocated a buffer, nor are any cache hit/miss checks performed.

[0077] Upon its dispatch from the memory-ordering unit 110, MFENCE is blocked by the L1 cache controller 120 if there are any outstanding operations in the L1 cache controller 120 not yet globally observed. If blocked, the MFENCE instruction evicts any outstanding write combining buffers 132. Once the L1 cache controller 120 accepts the incoming MFENCE instruction, it is treated as a non-operation and is retired from the memory subsystem. Note that the L1 cache controller 120 accepts the incoming MFENCE instruction only when all L1 cache controller buffers are globally observed. Just like LFENCE, MFENCE is never allocated a buffer, nor are any cache hit/miss checks performed.

[0078] For testability and debug purposes, two non-user visible mode bits can be added to enable/disable the MFENCE and LFENCE macroinstructions. If disabled, the L1 cache controller unit 120 can treat the incoming MFENCE and LFENCE micro-operations as a non-operation, and it does not check for global observation of older instructions. Thus, MFENCE and LFENCE are not blocked if their outstanding buffers in the L1 cache controller 120 not yet globally observed.

[0079] In alternate embodiments, the hardware implementation of LFENCE can be mapped to that of MFENCE. The corresponding MFENCE micro-operations can be used for both macroinstructions. This embodiment would still satisfy the architectural requirements of LFENCE, since the MFENCE behavior is more restrictive.

[0080] The previous description of the embodiments is provided to enable any person skilled in the art to make or use the system and method. It is well understood by those in the art, that the preceding embodiments may be implemented using hardware, firmware, or instructions encoded on a computer-readable medium. The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. 

What is claimed is:
 1. A process comprising: receiving a load fencing instruction that separates memory load instructions into older loads and newer loads; allocating a load buffer in a memory ordering unit to the load fencing instruction; stalling dispatches of newer loads from a memory subsystem; retiring older loads from the memory subsystem; dispatching the load fencing instruction from the load buffer to a cache controller when all older loads from the memory subsystem are retired.
 2. The process of claim 1 wherein the cache controller is the closest cache controller to a processor.
 3. The process of claim 2 further comprising: retiring the load fencing instruction from the cache controller.
 4. The process of claim 3 wherein the retirement of all older loads from the memory subsystem is via the cache controller.
 5. The process of claim 3 wherein the retirement of all older loads from the memory subsystem is via the memory ordering unit.
 6. The process of claim 5 wherein the retirement of all older loads from the memory subsystem is indicated when a reorder buffer retirement pointer and a load buffer tail pointer point to the load buffer.
 7. A computer architecture comprising: a computer readable memory; a cache controller; a memory ordering unit with at least one load buffer wherein the memory unit receives a load fencing instruction that separates memory load instructions that access the computer readable memory into older memory loads and newer memory loads, allocates the load buffer the load fencing instruction, stalls dispatches of newer memory loads, and dispatches the load fencing instruction from the load buffer to a cache controller when all older memory loads are retired.
 8. The architecture of claim 7 wherein the cache controller is the closest cache controller to a processor.
 9. The architecture of claim 8 wherein the cache controller retires the load fencing instruction.
 10. The architecture of claim 9 wherein the cache controller retires of all older memory loads.
 11. The architecture of claim 9 wherein the memory ordering unit retires of all older memory loads.
 12. The architecture of claim 11 wherein the retirement of all older memory loads is indicated when a reorder buffer retirement pointer and a load buffer tail pointer point to the load buffer.
 13. Computer executable program code, stored on a computer readable medium, for operating a computer system by functionally configuring it to have a computer readable memory, a cache controller, a memory ordering unit with at least one load buffer, comprising program code means for: receiving a load fencing instruction that separates memory load instructions into older loads and newer loads; allocating a load buffer in a memory ordering unit to the load fencing instruction; stalling dispatches of newer loads from a memory subsystem; retiring older loads from the memory subsystem; dispatching the load fencing instruction from the load buffer to a cache controller when all older loads from the memory subsystem are retired; retiring the load fencing instruction.
 14. A process comprising: receiving a memory fencing instruction that separates memory access instructions into older access instructions and newer access instructions; allocating a store buffer in a memory ordering unit to the memory fencing instruction; stalling dispatches of newer access instructions; retiring older access instructions; dispatching the memory fencing instruction to a cache controller when all older access instructions are retired; retiring the memory fencing instruction from the cache controller.
 15. A process comprising: receiving a memory fencing instruction that decodes into a load fencing micro-operation and a memory-fencing micro-operation; separating load instructions into older memory loads and newer memory loads; separating memory access instructions into older access instructions and newer access instructions; allocating a load buffer in a memory ordering unit to the load fencing micro-operation; stalling dispatches of newer memory loads; retiring older memory loads from the memory ordering unit; dispatching the load fencing micro-operation from the load buffer to a cache controller when all older loads are retired; allocating a store buffer in a memory ordering unit to the memory fencing micro-operation; stalling dispatches of newer access instructions; retiring older access instructions; dispatching the memory fencing instruction to the cache controller when all older access instructions are retired; retiring the memory fencing instruction from the cache controller.
 16. A computer architecture comprising: a computer readable memory; a cache controller; a memory ordering unit with at least one store buffer wherein the memory unit receives a memory fencing instruction that separates memory access instructions into older access instructions and newer access instructions, allocates a store buffer in a memory ordering unit to the memory fencing instruction, stalls dispatches of newer access instructions, retires older access instructions, dispatches the memory fencing instruction to the cache controller when all older access instructions, retires the memory fencing instruction from the cache controller.
 17. A computer architecture comprising: a computer readable memory; a cache controller; a memory ordering unit with at least one store buffer wherein the memory unit receives a memory fencing instruction that decodes into a load fencing micro-operation and a memory-fencing micro-operation, separates load instructions into older memory loads and newer memory loads, separates memory access instructions into older access instructions and newer access instructions, allocates a load buffer in a memory ordering unit to the load fencing micro-operation, allocates a store buffer in a memory ordering unit to the memory fencing instruction, stalls dispatches of newer memory loads, retires older memory loads from the memory ordering unit, dispatches the load fencing micro-operation from the load buffer to a cache controller when all older loads are retired, stalls dispatches of newer access instructions, retires older access instructions, dispatches the memory fencing instruction to the cache controller when all older access instructions are retired, retires the memory fencing instruction from the cache controller.
 18. Computer executable program code, stored on a computer readable medium, for operating a computer system by functionally configuring it to have a computer readable memory, a cache controller, a memory ordering unit with at least one load buffer, comprising program code means for: receiving a memory fencing instruction that separates memory access instructions into older access instructions and newer access instructions; allocating a store buffer in a memory ordering unit to the memory fencing instruction; stalling dispatches of newer access instructions; retiring older access instructions; dispatching the memory fencing instruction to a cache controller when all older access instructions are retired; retiring the memory fencing instruction from the cache controller.
 19. Computer executable program code, stored on a computer readable medium, for operating a computer system by functionally configuring it to have a computer readable memory, a cache controller, a memory ordering unit with at least one load buffer, comprising program code means for: receiving a memory fencing instruction that decodes into a load fencing micro-operation and a memory-fencing micro-operation; separating load instructions into older memory loads and newer memory loads; separating memory access instructions into older access instructions and newer access instructions; allocating a load buffer in a memory ordering unit to the load fencing micro-operation; stalling dispatches of newer memory loads; retiring older memory loads from the memory ordering unit; dispatching the load fencing micro-operation from the load buffer to a cache controller when all older loads are retired; allocating a store buffer in a memory ordering unit to the memory fencing micro-operation; stalling dispatches of newer access instructions; retiring older access instructions; dispatching the memory fencing instruction to the cache controller when all older access instructions are retired; retiring the memory fencing instruction from the cache controller. 